.vitepress/theme/style.css (1)

13-15: Add an explicit keyboard focus state for action buttons.

You already style hover; adding :focus-visible keeps keyboard navigation feedback consistent.

♿ Suggested enhancement

 a.action-button:hover {
   background-color: var(--vp-button-brand-hover-bg);
 }
+
+a.action-button:focus-visible {
+  background-color: var(--vp-button-brand-hover-bg);
+  outline: 2px solid var(--vp-c-brand-1);
+  outline-offset: 2px;
+}

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.vitepress/theme/style.css around lines 13 - 15, Add an explicit keyboard
focus state for the action buttons by adding a corresponding
a.action-button:focus-visible rule (matching the existing a.action-button:hover
styling) so keyboard users see the same feedback as hover; update the CSS to
define background-color: var(--vp-button-brand-hover-bg) (and any outline or
box-shadow if needed for accessibility) for the a.action-button:focus-visible
selector to keep hover and keyboard focus consistent.

website/contribute/_index.md (1)

17-58: Use root-relative links for internal destinations.

These are internal docs routes, but they’re hardcoded to https://gardener.cloud/.... Prefer /contribute/... links to keep previews/base-path deployments and local navigation behavior consistent.

♻️ Proposed refactor

-    link: 'https://gardener.cloud/contribute/contribution-process/how-to-contribute'
+    link: '/contribute/contribution-process/how-to-contribute'
@@
-    link: 'https://gardener.cloud/contribute/developer-starter-kit/'
+    link: '/contribute/developer-starter-kit/'
@@
-    link: 'https://gardener.cloud/contribute/gardener/'
+    link: '/contribute/gardener/'
@@
-    link: 'https://gardener.cloud/contribute/extensions/'
+    link: '/contribute/extensions/'
@@
-    link: 'https://gardener.cloud/contribute/other-components/'
+    link: '/contribute/other-components/'
@@
-    link: 'https://gardener.cloud/contribute/dashboard/'
+    link: '/contribute/dashboard/'
@@
-    link: 'https://gardener.cloud/contribute/documentation/'
+    link: '/contribute/documentation/'

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@website/contribute/_index.md` around lines 17 - 58, Replace absolute
gardener.cloud URLs with root-relative paths in the CardGrid :cards arrays so
internal docs route links use '/contribute/...' instead of
'https://gardener.cloud/contribute/...'; update each card object in the CardGrid
props (e.g., the entries for 'Contributor Guide', 'Developer Starter Kit',
'Gardener', 'Extensions', 'Other Components', 'Dashboard', and 'Documentation')
to use root-relative link strings that begin with '/contribute/...'.

website/blog/2023/03/03-27-high-availability-and-zone-outage-toleration.md (1)

452-452: Prefer root-relative clean URLs for internal links.

Line 452 uses deep relative links to _index.md, which are fragile during future moves. Use route paths directly (/contribute/#...) for stability.

♻️ Proposed refactor

-All channels for getting in touch or learning about the project are listed on our [landing page](../../../contribute/_index.md#community). We are cordially inviting interested parties to join our [bi-weekly meetings](../../../contribute/_index.md#bi-weekly-meetings).
+All channels for getting in touch or learning about the project are listed on our [landing page](/contribute/#community). We are cordially inviting interested parties to join our [bi-weekly meetings](/contribute/#bi-weekly-meetings).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@website/blog/2023/03/03-27-high-availability-and-zone-outage-toleration.md`
at line 452, Replace the deep relative internal links
"../../../contribute/_index.md#community" and
"../../../contribute/_index.md#bi-weekly-meetings" in the paragraph in
website/blog/2023/03/03-27-high-availability-and-zone-outage-toleration.md with
root‑relative route paths "/contribute/#community" and
"/contribute/#bi-weekly-meetings" so the links remain stable if the file is
moved; update both occurrences in the sentence referencing the landing page and
bi-weekly meetings.

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

.vitepress/theme/components/CardGridGroup.vue (1)

6-21: ⚡ Quick win

Use container/content-driven observation, not only window.resize, for re-equalization.

Line 16 only reacts to viewport resize. Card widths/heights can also change on layout/content updates without a resize event, leaving stale min-height values until the user resizes manually.

♻️ Suggested patch

-<script setup lang="ts">
-import { ref, onMounted, onUnmounted } from 'vue'
+<script setup lang="ts">
+import { ref, onMounted, onUnmounted, nextTick } from 'vue'

 const container = ref<HTMLElement | null>(null)
+let resizeObserver: ResizeObserver | null = null
+let rafId = 0

 function equalizeCardHeights() {
   if (!container.value) return
   const cards = container.value.querySelectorAll<HTMLElement>('.card')
+  if (!cards.length) return
   cards.forEach(c => c.style.minHeight = '')
   const maxHeight = Math.max(...Array.from(cards).map(c => c.offsetHeight))
   cards.forEach(c => c.style.minHeight = `${maxHeight}px`)
 }
+
+function scheduleEqualize() {
+  cancelAnimationFrame(rafId)
+  rafId = requestAnimationFrame(equalizeCardHeights)
+}

 onMounted(() => {
-  equalizeCardHeights()
-  window.addEventListener('resize', equalizeCardHeights)
+  nextTick(scheduleEqualize)
+  window.addEventListener('resize', scheduleEqualize)
+  resizeObserver = new ResizeObserver(scheduleEqualize)
+  if (container.value) resizeObserver.observe(container.value)
 })

 onUnmounted(() => {
-  window.removeEventListener('resize', equalizeCardHeights)
+  window.removeEventListener('resize', scheduleEqualize)
+  resizeObserver?.disconnect()
+  cancelAnimationFrame(rafId)
 })
 </script>

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.vitepress/theme/components/CardGridGroup.vue around lines 6 - 21, The
component currently only re-equalizes in onMounted and on window.resize; update
it to observe layout/content changes by creating a ResizeObserver (and
optionally a MutationObserver) that watches container.value (and/or its child
.card elements) and calls equalizeCardHeights on changes, while keeping the
existing window resize handler; ensure both observers are created in onMounted
and properly disconnected in onUnmounted alongside removing the window listener
so equalizeCardHeights runs whenever card sizes or content change.